Proxy based backup and restore of hyper-v cluster shared volumes (CSV)

ABSTRACT

In one example, a method includes receiving, at a physical proxy node, a backup request from a client outside the cluster environment, the backup request identifies a VM that is to be backed up, and including data that resides on a virtual federated database that is an element of the cluster environment and to which respective databases of each node of the cluster environment are mapped, and the backup request is received at the physical proxy node due to the position of the physical proxy node in a PSOL. Next, initiating, with an agent at the physical proxy node, a save program on the physical proxy node, and initiating, with the save program, a secondary save process on the physical proxy node that is a federated backup process and includes reading the VM identification from the backup request, and backing up the VM identified in the backup request.

FIELD OF THE INVENTION

Embodiments of the present invention generally concern backing up andrestoring data. More particularly, embodiments of the invention relateto systems, hardware, computer-readable media, and methods for backingup and/or restoring data associated with applications that run inclustered environments.

BACKGROUND

Entities often generate and use data that is important in some way totheir operations. This data can include, for example, business data,financial data, and personnel data. If this data were lost orcompromised, the entity may realize significant adverse financial andother consequences. Accordingly, many entities have chosen to back upsome or all of their data so that in the event of a natural disaster,unauthorized access, or other events, the entity can recover any datathat was compromised or lost, and then restore that data to one or morelocations, machines, and/or environments.

Systems, hardware, computer-readable media, and methods for backing upand/or restoring data may vary depending upon the nature of thecomputing environment in which associated applications are operating.For example, methods for backing up and restoring data generated inconnection with applications running in stand-alone environments may bequite different from methods for backing up and restoring data generatedin connection with applications running in clustered environments.Correspondingly, the challenges presented by operating in suchenvironments may be different as well, and clustered environments, inparticular, present some unique challenges to the backup and restorationof data.

To briefly illustrate, federated backup and restore functionality may beuseful in helping to provide application-specific backup and restoreoperations, while also helping to ensure that backup and restoreoperations in a cluster environment do not impair the operation ofproduction servers. However, an entity may prefer not to install abackup agent on every server in the cluster environment. Moreover, theentity may wish to be able to designate a particular server, or servers,in the cluster environment to be dedicated to backup and restoreoperations.

In light of the foregoing, it would be helpful to avoid the need toinstall a backup agent on all of the servers in a cluster environment.Likewise, it would be desirable for an entity to have some flexibilityin terms of designating a particular server, or servers, to performbackup and/or restore operations for one or more applications operatingin a cluster environment.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which at least some of the advantagesand features of the invention can be obtained, a more particulardescription of embodiments of the invention will be rendered byreference to specific embodiments thereof which are illustrated in theappended drawings. Understanding that these drawings depict only typicalembodiments of the invention and are not therefore to be considered tobe limiting of its scope, embodiments of the invention will be describedand explained with additional specificity and detail through the use ofthe accompanying drawings, in which:

FIG. 1 is directed to aspects of an example operating environment for atleast some embodiments of the invention;

FIG. 2 discloses an example of a backup and restore configuration;

FIG. 3 discloses an example of a server running a backup and restoreapplication;

FIG. 4 discloses aspects of an example method for performing a proxybased backup in a cluster environment;

FIG. 5 discloses aspects of an example system configuration inconnection with which a restore process may be performed;

FIG. 6 discloses aspects of an example UI that may be employed toidentify a proxy server for backup and/or restore operations;

FIG. 7 discloses aspects of an example method for performing a proxybased restore process in a cluster environment; and

FIG. 8 discloses aspects of an example method for executing a restorerequest.

DETAILED DESCRIPTION OF SOME EXAMPLE EMBODIMENTS

Embodiments of the present invention generally concern backing up andrestoring data. At least some embodiments are employed in clusteredenvironments. More particular example embodiments of the inventionrelate to systems, hardware, computer-readable media and methods forbacking up and/or restoring data associated with applications that runin clustered environments. These and/or other embodiments may beparticularly well suited for use with federated backup and/or restoresystems, hardware, computer-readable media and methods.

In at least some embodiments, one or more applications are installed andrunning in a cluster environment that includes a plurality of nodes,where one or more of the nodes may include, or constitute, a server. Theapplications may generate and/or cause the generation of data that isdesired to be backed up and, if necessary or desired, restored to one ormore locations, physical or virtual machines, or environments, forexample.

Prior to, or in connection with, a backup process to be performed in acluster environment, a user, such as a system administrator for example,can specify a particular node in the cluster as a proxy for performingthe backup of data generated by and/or in connection with one or more ofthe applications in the cluster environment. A prioritized list of nodesmay be employed and the backup can be performed by the first availablenode. In at least some embodiments, a default backup node may be definedalthough, if desired, a user may override the default and select analternative node in the cluster for performing the backup. In the eventthat none of the desired nodes are available for backup, the node towhich the cluster server name is resolved can be used.

For a restoration process to be performed in a cluster environment inconnection with backup data such as that described herein, a defaultrestore node may be defined although, if desired, a user may overridethe default and select an alternative node in the cluster as a proxy forperforming the restore. The restore node selection process can befacilitated by way of a graphical user interface (GUI) running on a nodeof the cluster. Once the restore node has been selected, whether bydefault or by a user, the restoration of the backup data to one or moretargets, such as a physical and/or virtual machine, can be performed.

As may be evident from the preceding discussion, and other disclosureherein, embodiments of the invention may provide various advantages,although it is not necessary, or required, that any particularembodiment(s) provide any particular advantage(s). Moreover, andconsistent with the foregoing, embodiments within the scope of one ormore claims may additionally, or alternatively, provide one or moreadvantages not specifically enumerated herein. Finally, to the extentthat possible advantages are enumerated herein, those may be present inone or more embodiments in any combination.

At least some embodiments of the invention may enable backup and/orrestoration of application data in a cluster environment, and may beparticularly useful in connection with federated backup and/or restoreoperations. As well, users may have the latitude to select any desirednode for the backup process, and/or for the restoration process,although default nodes for either or both can alternatively be defined.Finally, at least some embodiments of the invention may obviate the needto install a backup and/or restore agent on every node in the clusterwhere the applications are running.

A. Example Operating Environments

In general, embodiments of the invention may include and/or beimplemented in a cluster environment that includes a plurality of nodes.In some embodiments, the cluster environment comprises a Windows®Hyper-V Failover Cluster, although that is not required. One or more ofthe nodes can take the form of a server, such as a Windows® Hyper-Vserver for example, and/or other elements. One or more applications maybe hosted by one or more of the nodes of the cluster environment, andthe applications may generate and/or cause the generation of data thatis desired to be backed up and restored. For example, one, some, or allof the nodes in the cluster may host one or more virtual machines (VM),each of which may be running various applications. In at least someembodiments, the VMs may be created and run by a hypervisor, alsosometimes referred to as a virtual machine monitor (VMM), although useof a VMM is not required. The VMM, when present, can take the form ofsoftware, firmware, or hardware, or combinations of any of those.

The cluster environment may also include a disk or disks having one ormore volumes that are accessible for read and write operations, alsosometimes referred to as I/O operations, by all of the nodes within thecluster environment. One example of such a shared disk is a ClusterShared Volume (CSV) such as is employed in connection with Microsoft®Windows® Server applications such as the Microsoft® Windows® Server 2012Hyper-V application. The CSV includes a Windows® NT File System (NTFS)volume that is accessible by all nodes within an associated WindowsServer Failover Cluster. Multiple CSVs, or other disks, can be employedin a single cluster environment. It should be noted that the scope ofthe invention is not limited to the use of CSVs, nor to Windows® Serverapplications, and other shared disk configurations and/or otherapplications can alternatively be employed in other embodiments.

As the nodes in a cluster environment may each operate autonomously, andin connection with different respective databases, federated backup andrestore applications and methods are employed in at least someembodiments. In general, a federated approach to database managementinvolves the mapping of a plurality of different databases, such as therespective databases of the nodes in the cluster environment forexample, into a single federated database, one example of which is aCSV, although other types of shared disks can alternatively be used.Because the federated database is virtual, all users in the clusterenvironment have access to all cluster data, and the integrity of eachindividual database is maintained.

A variety of different backup and recovery applications can be used forfederated backup and restoration processes. One example of such a backupand recovery application is the EMC NetWorker backup and restoreapplication (NW), although other backup and restore applications canalternatively be employed in connection with one or more embodiments ofthe invention. In one particular example embodiment, the Network Modulefor Microsoft (NMM), a Microsoft-specific NetWorker module, is employedfor backup and restoration, although the scope of the invention is notlimited to the use or implementation of either NetWorker or NMM.Finally, in at least some embodiments, the backup and restoreapplication is hosted by a node, such as a server, that is not a part ofthe cluster environment, though such an arrangement is not required.

With the foregoing in mind, attention is directed now to FIG. 1 whichdiscloses aspects of an example operating environment 100. In general,the operating environment 100 includes a plurality of nodes 102, each ofwhich can access one or more shared disks 104 that store data 106 fromone or more of the nodes 102, where such data 106 may include one ormore of application data, system and other files, operating systems,file directories, and objects. While the example of FIG. 1 indicates twonodes 102, the operating environment 100 can include any number ofnodes, including three, or more, nodes. As well, the shared disks 104may be virtual disks, physical disks, or a combination of virtual andphysical disks.

One, some, or all of the nodes 102 may comprise a server. One, some, orall of the nodes 102 may include a plurality of virtual machines (VM)102A created and/or run by a virtual machine monitor (VMM) 102B. Aswell, one or more of the nodes 102 may include hardware 102C such asdisk drives, processors, computer readable media carrying executableinstructions for one or more applications, wireless and/or hardwiredcommunication hardware, RAM, ROM, flash memory, I/O devices, datastorage elements, or any combination of the foregoing.

In some more particular embodiments, the operating environment 100comprises a Hyper-V Failover Cluster, one or more of the nodes 102comprise a Windows® Server 2012 Hyper-V server, and/or the shared disk104 comprises one or more CSVs, although none of the foregoingparticular implementations are required to be employed.

Finally, the operating environment 100 may comprise or constitute acloud computing environment. For example, one or more nodes 102 maycomprise elements of a cloud computing environment.

B. Example System Configuration Backup

With reference now to FIG. 2 , and continued attention to FIG. 1 ,details are provided concerning an example system configuration inconnection with which a backup process, such as a federated backupprocess for example, may be performed. Except as may be noted elsewhereherein, the operating environment 200 of FIG. 2 may be the same, oridentical, to the operating environment disclosed in FIG. 1 and,accordingly, the discussion of FIG. 1 is applicable as well to FIG. 2 .As indicated in FIG. 2 , the operating environment 200 may include aplurality of nodes 202, designated “Node A” and “Node B” in the exampleof FIG. 2 . One or more of the nodes 202 can include one or more VMs202A and a VMM 202B. As well, one or more of the nodes 202 may includehardware 202C. While one or more of the nodes 202, like nodes 102, canbe identically configured, that is not required. As in the case of theoperating environment 100, the operating environment 200 may operate inconnection with one or more shared disks (not shown in FIG. 2 ), such asCSVs for example.

Moreover, the operating environment 200 may comprise or constitute acloud computing environment. For example, one or more nodes 202 maycomprise elements of a cloud computing environment.

As further disclosed in FIG. 2 , a backup and restore server 300 isarranged to coordinate with one of the nodes 202 to back up one or moreshared disks (not shown in FIG. 2 ) of the operating environment 200. Inthe example of FIG. 2 , the backup and restore server 300 is locatedremotely from the operating environment 200.

In general, the backup and restore server 300 may host a backup andrestore application 302 operable to perform a federated backup of theoperating environment 200, or operating environment 100, by backing upone more shared disks associated with the operating environment. In oneexample embodiment, the backup and restore server 300 is an EMCNetWorker server running the NetWorker application, although any othersuitable applications can alternatively be employed. Where the EMCNetWorker application is utilized, a module such as the Network Modulefor Microsoft (NMM) may be employed for backup and restore procedures,although that is not required.

With reference now to FIG. 3 , one example of a host 400, in the form ofa backup and restore server for example, and associated hardware isdisclosed. The host 400 can comprise any of a variety of host typesincluding, by way of example only, servers (e.g., a file server, anemail server, or any other type of server), computers (e.g., desktopcomputers, laptop computers, tablet devices, smartphones), virtualmachines, databases, or any combination thereof.

In the example of FIG. 3 , the host 400 is a machine, such as acomputing device, that includes a memory 402, one or more processors404, storage media 406, I/O device 408, and data storage 410. As well,one or more applications 412, such as a backup and restore applicationfor example, are provided that comprise executable instructions. One ormore nodes of an operating environment, such as the operatingenvironments 100 and 200 for example, may be configured similarly, oridentically, to the host 400.

C. Example Backup Process

Turning now to FIG. 4 , details are disclosed concerning aspects of anexample method 450 for performing a proxy based backup in a clusterenvironment. The method 450 begins at 452 where a proxy server isselected for the backup. Selection of the proxy server can be effectedmanually, or automatically. In the latter case, the proxy server can beset to a user-defined, or other, default. In one example of a manualselection process, a user, such as an administrator for example, canspecify a preferred server order list, which may also be referred to asa PSOL.

Where a PSOL is employed, the backup will be performed from the firstavailable server in the list. If none of the servers in the list areavailable, the backup may be performed from the node to which ‘ClusterServer Name’ is resolved. The PSOL can be defined, for example, asapplication information in the client resource of ‘Cluster Server Name’thus: NSR_FEDERATED_PSOL=server1, server2, server 3. The PSOL can bedefined in any other suitable fashion however, and the scope of theinvention is not limited to the foregoing example.

One useful aspect that may be realized by the aforementioned proxyserver approaches, discussed in more detail below, is that there is noneed for a backup agent to be installed on each of the servers in thecluster. Instead, the proxy server can be simply defined by default, orspecified on an as-needed basis by a user. These approaches can reduce,or eliminate, the need to impose a backup processing load on productionservers in the cluster.

After a proxy server for the backup has been selected, the method 450proceeds to 454 where the data backup process begins. As used herein,the term ‘data’ is intended to be broadly construed and includes, but isnot limited to, application data, system and other files, operatingsystems, file directories, file systems, objects, virtual machines, andshared disks such as CSVs. In some embodiments, a command such as the‘savegrp’ command used in connection with EMC NetWorker can be used toidentify, and initiate the backup of, the data of interest.

At 456, a backup request is generated and sent to the proxy server thatwas selected to perform the backup. The backup request can then be usedto initiate the backup. These processes can be implemented in a varietyof ways, one example of which follows.

With reference to the particular example of NetWorker, the ‘savegrp’command uses the ‘nsrjobd’ daemon, a NetWorker server daemon, to startthe backup of the identified data. More specifically, the ‘nsrjobd’daemon uses a client side module, such as ‘nsrexecd’ for example, forremote execution of the job request, that is, the backup of theidentified data. The ‘nsrexecd’ resides on the proxy server that is toperform the backup, the Cluster Server Client in this illustrativeexample. While this illustrative example employs a daemon, any otherstructure, device, code, program, or combination of the foregoing, canalternatively be employed.

After the backup request has been received at the proxy server, theprocess 450 advances to 458 where a backup process identified by thebackup request is initiated at the proxy server. The foregoing can beimplemented in a variety of ways, one example of which follows.

With continued reference to the NetWorker example, the client side‘nsrexecd’ forwards a job request, received from the ‘nsrjobd’ daemon,to a snapshot agent ‘nsrsnap’ for further processing. In particular, thesnapshot agent ‘nsrsnap’ can initiate the NMM nsrsnap_vss_save programas a primary backup process. This primary process then begins asecondary nsrsnap_vss_save process on the proxy server that was selectedto perform the backup. This secondary process invokes Hyper-V and CSVVSS (Volume Shadow Copy Service) writers to determine virtual machinesand cluster shared volumes to be backed up, and then performs thebackup. Specifically, Hyper-V uses the VSS to backup and restore virtualmachines. The backup can be stored in any suitable location. In at leastsome embodiments, the backup is stored at the proxy server thatperformed the backup process, although the backup could be stored inadditional, or alternative, locations as well.

D. Example System Configuration Restore

In general, a restore operation within the scope of the presentinvention can be initiated either on a node in a cluster environment, oron a node, such as a client for example, outside of the clusterenvironment. Turning now to FIG. 5 , details are disclosed concerningaspects of an example system configuration in connection with which arestore process may be performed. In the example of FIG. 5 , a restoreprocess can be initiated on a node outside of the cluster environment.In general, the operating environment 500 may be substantially the sameas the operating environment 200 or operating environment 100.Accordingly, only certain distinctions between the operating environment500 and operating environments 100 and 200 are addressed below.

Similar to the operating environment 200 and the operating environment100, the operating environment 500 may comprise a cluster environmentthat includes a plurality of nodes, such as nodes 502A and 502B forexample. As indicated in the example of FIG. 5 , nodes 502A and 502B areboth server cores. As such, it may not be possible or desirable, in somecircumstances at least, to initiate a restore process from those clusternodes. Of course, other arrangements can be employed where one or morenodes of a cluster environment do not comprise server cores. Moreover,the operating environment 500 may comprise or constitute a cloudcomputing environment. For example, one or more of the nodes 502A and502B may comprise elements of a cloud computing environment.

In addition to the nodes 502A and 502B, the operating environment 50 mayinclude one or more external nodes 502C, such as a remote client forexample, and external node 502D, such as a backup and restore server forexample. The external node 502C may include a user interface (UI) 504that can be used by an administrator or other user to initiate a clusterlevel restore operation. In one example embodiment, the UI 504 is a NMMUI, an example of which is disclosed in FIG. 6 , discussed below.

In addition to the UI 504, the external node 502C includes a module 506,such as plug-in, that is operable to implement and/or cause theimplementation of, among other things, one or more desired backuppolicies. One example of such a plug-in is the HyperVPlugIn, althoughalternative plug-ins and modules can be employed. Node 502A, which maycomprise an aliasing node, includes an agent 508 that operates at thedirection of the module 506. In the example embodiment where the module506 is implemented as the HyperVPlugIn, the agent 508 may comprise theHyper-V agent ‘nmcsc.’

With continued reference to FIG. 5 , the external node 502D may includea module 510, such as the ‘nsrjobd’ daemon for example, that cooperateswith the module 506 and a module 512, such as ‘nsrexecd’ for example, tofacilitate one or more aspects of a restore process, as discussed infurther detail elsewhere herein. As well, the external node 502D mayinclude a recovery module 514. Where restore operations are performed ina Hyper-V CSV environment, the recovery module 514 may comprise the‘nsrsnap_vss_recov’ program.

Turning now to FIG. 6 , details are provided concerning an example of UI600 that may be used in the selection of proxy server for a restoreoperation. While the example disclosed in FIG. 6 is specific to theHyper-V environment, it should be understood that various other forms ofa UI may be employed, and the scope of the invention is not limited tothe particular example of FIG. 6 . As discussed in more detail elsewhereherein, the UI 600 can be invoked on a node within a cluster environmentor, alternatively, on a node that is not part of that clusterenvironment.

The UI 600 includes a proxy server tab 602 that, when selected by auser, enables the user to select a proxy server for a restore operation.In particular, a radio button 604 enables a user to specify a localserver, or current host server, for the recovery operation.Alternatively, a user may employ a radio button 606 to choose a specificserver from a drop-down list 608.

E. Example Restore Process

Turning now to FIG. 7 , and with continuing reference to FIG. 5 ,details are disclosed concerning aspects of an example method 700 forperforming a proxy based restore process in a cluster environment. Ingeneral, FIG. 7 is directed to an example method for restoring one ormore machines, where the restore process is initiated on a client orother node outside a cluster environment.

The method 700 begins at 702 where information is obtained concerningthe configuration of the cluster environment and the configuration ofthe machine or machines, such as VMs, that are to be restored. Thisprocess can be performed in a variety of ways, one example of which isdiscussed below.

In particular, and with reference to the example of the Hyper-V CSVenvironment, a user may start an NMM UI on a remote client that isoutside the cluster environment and, using the UI, navigate to theHyperVPlugIn on that client, and commence a restore process, such as acluster level restore process. If, on the other hand, the NMM UI isstarted on a node that is in the cluster environment, that node willbecome the default node for restore operations. That is,nsrsnap_vss_recov.exe is spawned on the local host in this scenario.

Once the user has navigated to the HyperVPlugIn, the HyperVPlugInconnects to a corresponding agent, such as the Hyper-V agent ‘nmcsc,’located on a cluster aliasing node and obtains cluster and VMconfiguration information from the agent.

As part of this initial process, the user may select a proxy node in thecluster on which restore operations will be performed. This selectionmay be facilitated by a UI such as is disclosed in FIG. 6 . The proxynode in this particular example is the node on whichnsrsnap_vss_recov.exe will be spawned. As noted elsewhere herein, theproxy node for a restore operation can be set by default. In one defaultscenario, nsrsnap_vss_recov.exe is spawned on the aliasing node (see,e.g., FIG. 5 ) that is, the node to which ‘Cluster Server Name’resolves.

With continued reference now to FIG. 7 , a restore request that includesa restore command for one or more machines, such as VMs, on a node ofthe cluster environment is sent 704. In one example implementation, thisjob request is sent from a remote client outside the cluster environmentto a backup and restore server that is also outside the clusterenvironment. In the context of a Hyper-V CSV environment, this processcomprises the use of the HyperVPlugIn to send a restore command for oneor more VMs to ‘nsrjobd’ on a backup and restore server.

The restore request is then executed 706. In particular, the machine(s)identified in the restore request are restored. In some embodiments, thehandling and execution of the restore request may involve first sendingthe restore request from a backup and restore server to a module, suchas a client side module ‘nsrexecd’ for example, on the proxy server thatis to perform the restore process. The client side module may thenforward the restore request to a recovery program on the proxy server,and the recovery program then restores the machine(s) identified in therecovery request. One particular implementation of the execution 706 ofa restore request is addressed below in the discussion of FIG. 8 .

Finally, confirmation that the restore process has been completed issent 708. In some embodiments, this confirmation is sent from the backupand restore server to the remote client from which the restore processwas initiated.

F. Execution of Restore Request in Restore Process

Turning now to FIG. 8 , and with continued reference to FIG. 5 , detailsare disclosed concerning aspects of an example method 800 for executinga restore request, such as the restore execution process 706 that mayoccur in connection with a restore process exemplified by method 700. Ingeneral, the method 800 concerns processes performed by, or at least inassociation with, the recover program nsrsnap_vss_recov.exe, which maybe spawned, and reside, on an aliasing node. Any other suitable recoverprogram(s) can alternatively be employed however.

In some embodiments, a Hyper-V VSS Writer is invoked prior to, or aspart of, the method 800. The Hyper-V VSS Writer may use aninfrastructure such as Windows Management Instrumentation (WMI) toobtain management and other data concerning the restore operation,and/or WMI can be used to perform elements of the restore operation.

The example method 800 begins at 802 where the cluster resource groupsthat manage the machines, such as VMs, to be restored are identified.Next, the components of the backed up machines, and any Hyper-V VSSWriter metadata are loaded 804, and the files to be restored aredetermined 806. This determination may be made, for example, byinterfacing with the Hyper-V VSS Writer or WMI.

The VM(s) to be restored, and the VM configuration resources are thenbrought offline 808. In some embodiments, this may be accomplished, forexample, through the use of one or more cluster application programinterfaces (API). Next, the offline VM(s), if any exist, are removed 810from the node where the restoration is to occur.

Once the VM(s) are removed, the node is then ready for restoration ofthe backed up VM(s). Accordingly, the backed up VMs are then restored812 to the node. In some embodiments, this may be accomplished, forexample, by interfacing with the Hyper-V VSS Writer or WMI. Where theHyper-V VSS Writer is employed, restoration of the VM(s) will bring upthe VM(s) in the Hyper-V Manager to enable further processing, ifdesired, of those VM(s) using the Hyper-V Manager.

Once the VM(s) have been restored to the target node, the restored VM(s)and the VM configuration resources can then be brought online 814. WMIAPIs or comparable mechanisms are then used to enable the restored VM(s)to serve as cluster-wide VM(s) 816. Finally, one or more of the restoredVM(s) can be migrated 818 to their original nodes if desired and if notalready resident there.

G. Example Computing Devices and Associated Media

The embodiments disclosed herein may include the use of a specialpurpose or general-purpose computer including various computer hardwareor software modules, as discussed in greater detail below. A computermay include a processor and computer storage media carrying instructionsthat, when executed by the processor and/or caused to be executed by theprocessor, perform any one or more of the methods disclosed herein.

As indicated above, embodiments within the scope of the presentinvention also include computer storage media, which are physical mediafor carrying or having computer-executable instructions or datastructures stored thereon. Such computer storage media can be anyavailable physical media that can be accessed by a general purpose orspecial purpose computer.

By way of example, and not limitation, such computer storage media cancomprise hardware such as solid state disk (SSD), RAM, ROM, EEPROM,CD-ROM, flash memory, phase-change memory (“PCM”), or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother hardware storage devices which can be used to store program codein the form of computer-executable instructions or data structures,which can be accessed and executed by a general-purpose orspecial-purpose computer system to implement the disclosed functionalityof the invention. Combinations of the above should also be includedwithin the scope of computer storage media.

Computer-executable instructions comprise, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing device to perform a certain function orgroup of functions. Although the subject matter has been described inlanguage specific to structural features and/or methodological acts, itis to be understood that the subject matter defined in the appendedclaims is not necessarily limited to the specific features or actsdescribed above. Rather, the specific features and acts disclosed hereinare disclosed as example forms of implementing the claims.

As used herein, the term ‘module’ or ‘component’ can refer to softwareobjects or routines that execute on the computing system. The differentcomponents, modules, engines, and services described herein may beimplemented as objects or processes that execute on the computingsystem, for example, as separate threads. While the system and methodsdescribed herein can be implemented in software, implementations inhardware or a combination of software and hardware are also possible andcontemplated. In the present disclosure, a ‘computing entity’ may be anycomputing system as previously defined herein, or any module orcombination of modulates running on a computing system.

In at least some instances, a hardware processor is provided that isoperable to carry out executable instructions for performing a method orprocess, such as the methods and processes disclosed herein. Thehardware processor may or may not comprise an element of other hardware,such as the computing devices and systems disclosed herein.

In terms of computing environments, embodiments of the invention can beperformed in client-server environments, whether network or localenvironments, or in any other suitable environment. Suitable operatingenvironments for at least some embodiments of the invention includecloud computing environments where one or more of a client, server, ortarget virtual machine may reside and operate in a cloud environment.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A method, comprising: receiving, at a physicalproxy node, a backup request from a client outside the clusterenvironment, wherein the backup request identifies a virtual machinethat is to be backed up, the virtual machine comprising data thatresides on a virtual federated database that is an element of thecluster environment and to which respective databases of each of aplurality of nodes of the cluster environment are mapped, and whereinthe backup request is received at the physical proxy node due to theposition of the physical proxy node in a preferred server order list(PSOL); after receipt of the backup request at the physical proxy node,initiating, with an agent residing at the physical proxy node, a saveprogram on the physical proxy node; after the save program has beeninitiated on the physical proxy node, initiating, with the save program,a secondary save process on the physical proxy node, wherein thesecondary save process is a federated backup process and comprises:reading the virtual machine identification from the backup request; andcreating a backup of the virtual machine identified in the backuprequest; loading the backup of the virtual machine; taking the virtualmachine offline after the backup of the virtual machine has been loaded;after the virtual machine has been taken offline, removing the virtualmachine from the node where it resides; restoring the backup of thevirtual machine to a node of the cluster environment; bringing therestored virtual machine online after the backup of the virtual machinehas been restored; and after the restored virtual machine has beenbrought online, enabling the restored virtual machine as a cluster-widevirtual machine.
 2. The method as recited in claim 1, wherein thephysical proxy node at which the backup request is received comprises:one or more virtual machines; a virtual machine monitor operable to runthe one or more virtual machines; and hardware, the hardware comprisingany one or more of disk drives, wireless and/or hardwired communicationhardware, RAM, ROM, flash memory, I/O devices, data storage elements, orany combination of the foregoing.
 3. The method as recited in claim 1,wherein the cluster environment in which the physical proxy node residesis a Hyper-V Failover cluster.
 4. The method as recited in claim 1,wherein the secondary process is performed by a program residing on thephysical proxy node.
 5. The method as recited in claim 1, wherein theagent comprises a snapshot agent.
 6. A method, comprising: loading abackup of a virtual machine, the backup of the virtual machine havingbeen created by a federated backup process involving a physical proxynode, and the virtual machine comprises data that resides on a virtualfederated database that is an element of a cluster environment and towhich respective databases of each of a plurality of nodes of thecluster environment are mapped; taking the virtual machine offline afterthe backup of the virtual machine has been loaded; after the virtualmachine has been taken offline, removing the virtual machine from thenode where it resides; restoring the backup of the virtual machine to anode of the cluster environment; bringing the restored virtual machineonline after the backup of the virtual machine has been restored; andafter the restored virtual machine has been brought online, enabling therestored virtual machine as a cluster-wide virtual machine.
 7. Themethod as recited in claim 6, wherein the physical proxy node comprisesa server core.
 8. The method as recited in claim 6, wherein the restoredvirtual machine resides on the physical proxy node.
 9. The method asrecited in claim 6, wherein the operations further comprise loadingmetadata associated with the backup of the virtual machine.